Anybody used link by attribute and used the "Target to source" link direction, as opposed to the conventional "Source to target" option? I have used this on some modules lately and the links tend to disappear. I can see the in-link indicators and actually see what modules and absolute numbers the link comes from. However, when the source module is opened, or the object properties of the target object are accessed, the indicators disappear. Also, when the source module is opened, there are no out-link indicators...regardless if the target module has been opened or not. |
Re: Link by Attribute - Target to Source Paul Miller Specification Practices Specialist EuroCyber Melbourne, Australia |
Re: Link by Attribute - Target to Source A user called reporting that all his links had disappeared. A quick investigation revealed that in the target module the inlink indicators were visible, but the source did not show any outlink indicators. Opening the object properties either of source or target made the inlink indicators disappear too. But: history of source objects showed creation of links. That is how I was able to recreate the links. Now two days later the user calls again telling that the links have disappeared again. Frustrating. |
Re: Link by Attribute - Target to Source |
Re: Link by Attribute - Target to Source kabr - Tue Mar 31 04:06:25 EDT 2009 kabr - did you gather all the history information manually, or did you write a script to automate this reporting? |
Re: Link by Attribute - Target to Source [1] There was an old v5.2 bug where links were 'invisible' in the target module but were visible in the source. The solution was to write a dxl to loop through all source objects and loop through all outgoing links. Simply accessing the links in the Source made them visible again in the Target. Looking closer at that old code, I see that I opened the source Edit, got the handle of the target module of each and every link, and opened it Edit as well, and then got the handle of the target object. The code didn't actually change anything, but opening 'edit' and then force 'saving' seems to be required. Wrap this code in a big loop that plows through all the modules in a Project. Code hasn't been used in years since the symptom has not surfaced. [2] There is a problem with creating a link in an Edit module, and then forgetting to save that source module before closing it. IIRC from v5 days, the 'unSaved' command incorrectly says the module doesn't need saving. IIRC, the links are seen for a while in the Target module. [3] There may be a problem with failing to save the Link Module after you create a link set therein. [4] I have a nagging bad memory of access problems to link modules; something weird like you can create a link in a link module with RC access, but it really requires RM access to save it OK. [5] I have a long time nagging memory of the Link-By-Attribute GUI where you change the desired direction of the links, but the background code fails to swap the default link module to correspond. That is, it figures out the default link module for the source-to-target, but when you switch directions it uses the original source-to-target link module, failing to recalculate for the new default link module. That conflicts with the linkset pairings for the target. BINGO, I knew if I babbled I'd come up with it. >Louie |
Re: Link by Attribute - Target to Source @ llandale: [1] for me it is the other way round: inlinks are visible (until object properties are opened), outlinks are not [2] not here: (re)created the links, pressed the save button. next day outlinks have disappeared [3] no, link module has not been touched [4] as admin I have RMCDA on link modules [5] our links were not created via Link-by-Attribute but manually Support seems to be clueless. they offered their link-repair tool, which removes stale links (afaik). Karl |
Re: Link by Attribute - Target to Source kabr - Wed Apr 01 08:24:14 EDT 2009 Support gave me the same solution as Karl...a tool to delete the links. I keep telling them that is not what I intend to do, but they keep posing that as the solution. They even mentioned said, and I quote, "this is how the application is designed and once a link is deleted it cannot be restored". Unfortunately, they do not understand the actual issue and refuse to open their minds to any sort of intelligence. The latest update is that I have requested a script to report the history of created links for modules. At least I can get the info in a spreadsheet and work it from there. Corey |
Re: Link by Attribute - Target to Source Perhaps you can add code to open all the other modules, then run a loop on all your links using this function, printing as much information as you can; perhaps: bool IsGood = fGetLinkInfo(lnk, cl_DoInLinks, NameOther, NameLM, oLinked) print IsGood "\t<">\t<">\t" if (!null oLinked) "" print (identifier(oLinked)) "" print "\n" I suppose its remotely possible you'll get enough information about the 'missing' links to figure out what's really going on. >Louie Attachments attachment_14236398_fGetLinkInfo_Temp.dxl |